-
Notifications
You must be signed in to change notification settings - Fork 188
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
chore: Uses official CLI GH action in TF clean-up workflow #1718
Conversation
- name: Checkout | ||
uses: actions/checkout@v4 | ||
with: | ||
sparse-checkout: | | ||
scripts | ||
- uses: mongodb/atlas-github-action@main |
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.
- uses: mongodb/atlas-github-action@main | |
- uses: mongodb/atlas-github-action@v0.2.0 |
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.
@andreaangiolillo it's the recommended way in the instructions: https://github.com/marketplace/actions/atlas-cli-github-action
also I suppose being our GH action, it's not so a big (security) problem to use main.
@matt-condon WDYT is better to use here? (if v0.2.0 , should we change example / doc?
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.
Using master is a bad practice as we may push a bug unintentionally. I will update the description to be at least @latest (still not a best practice but at least an official release)
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.
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.
@andreaangiolillo i see your point of master having a bug even if not published. keeping v0.2.0 at the moment as latest doesn't work.
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.
using @v0
should also be an option if you always want the latest published version without breaking changes
Edit: for clarity, would need to publish a new version
- shell: bash | ||
run: atlas --version |
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.
Why do you need this?
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 found it interesting in case something fails to compare with local atlas version
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.
but you're right we won't normally use it, removed
This reverts commit f10a015.
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.
LGTM
|
Description
Uses official CLI GH action in TF clean-up workflow.
Link to any related issue(s): https://jira.mongodb.org/browse/CLOUDP-215921
Type of change:
Required Checklist:
Further comments