-
Notifications
You must be signed in to change notification settings - Fork 1
feat: add support to create resource key #90
New issue
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
Conversation
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
|
The Re-running the pipeline |
|
/run pipeline |
|
Failing due to the earlier resource key being destroyed |
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See comments
|
|
||
| resource "ibm_resource_key" "resource_key" { | ||
| name = var.manager_key_name | ||
| count = var.disable_access_key_creation ? 0 : 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wont this be a breaking change without a moved block? Why did upgrade test not fail?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, when I ran locally terraform is understanding that we've added a count around the resource block. I will attach the screenshot here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you sure? Usually a moved block is required when we add a count
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
final few comments
|
|
||
| resource "ibm_resource_key" "resource_key" { | ||
| name = var.manager_key_name | ||
| count = var.disable_access_key_creation ? 0 : 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you sure? Usually a moved block is required when we add a count
|
/run pipeline |
| sensitive = true | ||
| } | ||
|
|
||
| output "manager_key_name" { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should keep this output, but it should be renamed to access_key_name
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I remember that I have renamed this and added it back, somehow it is not in the final push :(
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@iamar7 1 final comment
|
/run pipeline |
Resolved |
|
🎉 This PR is included in version 1.10.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |

Description
Resolves: #28
Release required?
x.x.X)x.X.x)X.x.x)Release notes content
This release added a new
disable_access_key_creationflag (default: false) to allow opting out of automatic access key creation and added an additional method to support multiple resource keys. You can now define multiple keys by adding more entries to theresource_keyslist.Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
Checklist for reviewers
For mergers