-
Notifications
You must be signed in to change notification settings - Fork 290
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
Minor updates to user docs - concepts #7345
Conversation
- sentence flow, headings, capitalisation
|
|
||
In a shared AWS account for a business unit, untaggable billable items such as Data Transfer become impossible to attribute to an application. | ||
In a shared AWS account for a business unit, untaggable billable items such as Data Transfer cannot easily be attributed to a particular application. |
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.
untaggable billable items such as Data Transfer cannot easily be attributed to a particular application
Is this still the case (I don't have access to any cost allocation billing report to check)? https://repost.aws/questions/QUSiF9OHXiSqmYWZ4BbnAKeA/data-transfer-tagging
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.
Not entirely sure. This may be a comment from an historic perspective. It could now be, with tags and other items included, they can be. As you say access to specifics would be best to check this.
- people tend to go for the easiest option, which creates technical debt further down the line | ||
- infrastructure quickly becomes hard to track | ||
- it can become tangled and messy | ||
- doesn't support the central alignment we're trying to achieve |
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.
doesn't support the central alignment we're trying to achieve
I'd prefer to reword this *that this be reworded, as it's not clear to me exactly what this means
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.
If you feel this needs to be reworded you could send out an example to the whole team to see if anyone has complaints/suggestions.
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.
Personally? This is an early way of describing what P&A exists to do through hosting teams.
|
|
|
update lychee command to use config toml
|
@@ -1,6 +1,13 @@ | |||
# Modernisation Platform: environments bootstrapping |
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 think this README might have been intended for the parent directory (terraform/environments/bootstrap
)
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.
Agreed. Feel free to move it!
|
|
No associated issue. An update to the 'Concept' section of the user guide, and addition of a workflow to run on docs PRs to check whether external links are working.
Also includes:
Checklist (check
x
in[ ]
of list items)Additional comments (if any)
{Please write here}