-
Notifications
You must be signed in to change notification settings - Fork 137
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
Add Vendordata to metadata #579
Conversation
6fffe7b
to
f98e402
Compare
Codecov Report
@@ Coverage Diff @@
## main #579 +/- ##
==========================================
+ Coverage 44.43% 44.52% +0.09%
==========================================
Files 61 61
Lines 3497 3519 +22
==========================================
+ Hits 1554 1567 +13
- Misses 1862 1870 +8
- Partials 81 82 +1
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
f98e402
to
cd45f1a
Compare
3d17ba8
to
3d501bf
Compare
3d501bf
to
1822556
Compare
@chrisdoherty4, mind taking a look at this? |
This seems OK for the Kube back-end. Do we need anything in the database? Do we need a discussion around continued database support? |
I think we're good to merge this! |
Signed-off-by: Marques Johansson <[email protected]>
Signed-off-by: Marques Johansson <[email protected]>
rebased |
Description
Adds a vendordata key to the metadata structure. This will be used by tinkerbell/hegel#62
Why is this needed
How Has This Been Tested?
How are existing users impacted? What migration steps/scripts do we need?
The addition of a vendordata path will allow for differentiation between "userdata" and "vendordata" as described in https://cloudinit.readthedocs.io/en/latest/topics/vendordata.html
Checklist:
I have: