-
Notifications
You must be signed in to change notification settings - Fork 42
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
Glue21 JSON #340
Glue21 JSON #340
Conversation
We are no longer using the refresh style
Terraform Format and Style 🖌
|
Terraform Format and Style 🖌
|
Terraform Format and Style 🖌
|
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.
Minor suggestions
export S3_BUCKET_NAME | ||
export RCLONE_CONFIG_S3_ACL=private | ||
export RCLONE_CONFIG_S3_NO_CHECK_BUCKET=true | ||
rclone copy site.json "s3:$S3_BUCKET_NAME/$SITE_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 would add a decision record for using rclone instead of Wrangler https://developers.cloudflare.com/r2/objects/upload-objects/
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 still want to be cloudflare agnostic, rclone was the tool I was aware that could be used without much hassle.
BTW, we don't have decision records (yet). I guess if we want to get started with them, they should come as part of the PR, no?
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'm also in favour of using well known generic and independent tools like rclone instead of cloudflare owned stuff, at least when it can be avoided and does not have a clear/decisive benefit.
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.
that's fine, but write a decision record for it (using e.g. https://github.com/npryce/adr-tools)
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 have made an attempt to use ADRs, somehow considering this as "Accepted" already. On the learning curve for this, so guidance on how to better use it is welcomed
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.
That's interesting.
It would be good to document this kind of things/guidelines/suggestions for repo management somewhere.
We could start by adding it to some internal documentation page for GitHub (like in our internal wiki).
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.
Added a note to https://confluence.egi.eu/display/Office/GitHub
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.
Thanks!
Lately I realised that we could also use the repo template to document this: https://github.com/EGI-Federation/repository-template
Terraform Format and Style 🖌
|
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.
All looking good, thanks!
Just a minor comment below
Terraform Format and Style 🖌
|
Terraform Format and Style 🖌
|
Terraform Format and Style 🖌
|
🚢 |
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
🚢 🚢 🚢 🚢 |
Ansible deployment:
|
* Use https * Upgrade cloud-info-provider * Install rclone * Add json output and upload to S3 * Make linter happy * Remove VOs not in ops portal * Remove VO not in ops portal * Simplify management of tokens We are no longer using the refresh style * Fixes tested in the playground * Fix linter / testing issues * Fix tests * Add some docs * ADR * Linter is my friend
Summary
Publish JSON information as a way to get into a more modern information system.
The info will be published in a S3 bucket (available in the secrets of the GH Action)
Related issue :