Determine how to handle the "allowed-vm-sizes" file in CoA
BMurri opened this issue · comments
Describe the bug
TES is currently no longer looking for a Configuration
container, for compatibility with Terra. The TES deployer moved that file, but the CoA deployer continues to place it in the previous location, making it inaccessible and ineffective.
Steps to Reproduce
Deploy CoA.
Notice warnings in the TES logs about allowed-vm-sizes
file not being found at a different location than previously documented.
Look in the configuration container and note that the file is present in the previously documented location.
Expected behavior
Either TES can find that file in the location that the CoA deployer places it (with all of the other CoA configuration) or both CoA's deployer and the documentation are updated to indicate the new location of that file (along with moving it during upgrades).
Additional context
TBD