Closed sangee2004 closed 8 months ago
Just merged the fix. resolvedOfferings should look correct for the Acornfile given in this issue.
Tested with acorn version - v0.10.0-rc2-17-g1142dab8+1142dab8
Resolved offerings shows the right memory value set for the container from "-m" optioned used in the CLI as expected.
acorn version -
v0.10.0-rc2-9-g43dbcbf4+43dbcbf4
Steps to reproduce the problem:
acorn run -n test2 -m 128Mi .
resolvedOfferings
fieldResolved offerings shows the memory value set in Acornfile for the containers.
Expected Behavior: Resolved offerings should show the memory value set for the container from CLI which is what it gets deployed with.