Skip to content
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

Documentation could be clearer #2

Open
strus38 opened this issue Oct 26, 2022 · 1 comment
Open

Documentation could be clearer #2

strus38 opened this issue Oct 26, 2022 · 1 comment
Assignees

Comments

@strus38
Copy link

strus38 commented Oct 26, 2022

Hi
Could you add in the doc what is meant by:

The report depends on a Billingcode tag/label and vault name tag/label that will need to be added to the AWS EFS/GCP Filestore.

Are those labels specifics or free? could you give a working exemple?

Also could you add a directory: 'examples' with a dummy report so we can see what is inside?

Thanks a lot.

@mark-nimbix mark-nimbix self-assigned this May 26, 2023
@mark-nimbix
Copy link
Contributor

mark-nimbix commented May 26, 2023

Sorry for the late reply. This refers to the labels for GCP Filestore or the tags for AWS EFS. This is a mechanism to track several resources for a single customer and identify which storage item should be associated with which billing code.
In either case the code looks for labels or tags for GCP/AWS respectively with a key of your choosing.
Look at the helm values. The bctag and nametag values refer to the labels you add to the filestores.

https://github.com/nimbix/jxe-billing-report/blob/master/helm/values.yaml

I will try to make this more clear in future revisions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants