Great videos Mike, really instructive! I was trying to adapt this for my use case, and I noticed you are using variables like {COMPONENT_NAME} and {COMPONENT_VERSION} in the recipe file. These don't seem to be standard variables supported by gdk though, so they won't be replaced in the generated recipe on build if it's used elsewhere in the recipe (for example the way you're using them in the accessControl and the s3 URI). I want to use the component version added by the gdk build in the recipe s3 URI though, do you have any ideas on how to achieve this?
Thank you! As to your question, you're right that those variables aren't replaced. In the accessControl, that name field doesn't really affect anything, it just needs to be a unique name - the output file does stay as {COMPONENT_NAME}, but that's fine as a unique field. It is confusing, that's my fault for not updating it. For the S3 URI, I left that the same as the template for Python HelloWorld. It automatically replaces the bucket name, component name, and component version in the publish step - if you publish the component, then take a look at the component in the cloud, you'll see that the artifacts section has an S3 URI that contains the right information. If you want to change those fields elsewhere in your recipe, I don't know how to do that - but I would be interested in your use case!
Great videos Mike, really instructive! I was trying to adapt this for my use case, and I noticed you are using variables like {COMPONENT_NAME} and {COMPONENT_VERSION} in the recipe file. These don't seem to be standard variables supported by gdk though, so they won't be replaced in the generated recipe on build if it's used elsewhere in the recipe (for example the way you're using them in the accessControl and the s3 URI). I want to use the component version added by the gdk build in the recipe s3 URI though, do you have any ideas on how to achieve this?
Thank you! As to your question, you're right that those variables aren't replaced. In the accessControl, that name field doesn't really affect anything, it just needs to be a unique name - the output file does stay as {COMPONENT_NAME}, but that's fine as a unique field. It is confusing, that's my fault for not updating it.
For the S3 URI, I left that the same as the template for Python HelloWorld. It automatically replaces the bucket name, component name, and component version in the publish step - if you publish the component, then take a look at the component in the cloud, you'll see that the artifacts section has an S3 URI that contains the right information.
If you want to change those fields elsewhere in your recipe, I don't know how to do that - but I would be interested in your use case!
Thank you for the video Mike
Thank you for watching!!