We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have tried to dig into the documentation, but I can't find any good answer there.
What I want to know is, when is name in a resource's properties required?
name
properties
From what I can gather from the examples, the name of the resource is automatically injected as the name property as well?
For example, a compute.v1.address has a name property, and it gets set to the resource name, if it's omitted.
compute.v1.address
def generate_config(context): address = { 'name': context.env['name'], 'type': 'compute.v1.address', 'properties': { 'region': context.properties['region'], 'description': context.properties['description'] } } return {'resources': [address]}
Are there other properties that behave this way? A few lines about this behavior would be nice to have in the documentation.
Thanks!
The text was updated successfully, but these errors were encountered:
In general we use resource name for name and project from context as default project.
Sorry, something went wrong.
No branches or pull requests
I have tried to dig into the documentation, but I can't find any good answer there.
What I want to know is, when is
name
in a resource'sproperties
required?From what I can gather from the examples, the name of the resource is automatically injected as the
name
property as well?For example, a
compute.v1.address
has aname
property, and it gets set to the resource name, if it's omitted.Are there other properties that behave this way? A few lines about this behavior would be nice to have in the documentation.
Thanks!
The text was updated successfully, but these errors were encountered: