Closed rbability closed 4 years ago
That is by design.
New-BcImage creates the image you decide. New-BcContainer uses New-BcImage to "cache" an image and adds a naming algorithm to ensure that it selects the right image.
As I wrote, not a Bug, more a feature request :-) It would be very convenient to have the same behaviour for the -ImageName parameter when utilizing your cmdlets to populate a private repository.
Don't get me wrong, I am very happy with what we have right now, it already saves a lot of time.
After writing my previous response, I did reconsider and I agree that it indeed would be nice to have New-BcImage make the same defaulting of the tag. I will fix this.
Awesome, Thank you so much for all the hard work you put into this 👍
Note, that this fix will go into the BcContainerHelper module, NavContainerHelper will only get bug fixes. I will write a blog post about switching from NavContainerHelper to BcContainerHelper very soon, sorry for the inconvenience.
I don't see any inconvenience ;-) I'm glad you are doing this. Thanks for pointing that out, because I really thought they are the same (just different name), since there are BC Aliases for NAV cmdlets in the NavContainerHelper. I will switch ASAP then. Thanks for the heads up!
Shipped in BcContainerHelper 1.0.1
Describe the issue This is not an issue, probably more like a feature request.
New-NavContainer together with -ImageName creates an image which includes the Version in the auto-generated Tag name. New-BCImage however is just adding :latest as the tag when you use the -ImageName parameter and leave out the tag.
It would be fantastic if New-BCImage would follow the same principle as New-NavContainer in this regard. So you can pull the latest version of the Artifacts, let it create an image which automagically has the correct version in the Tag :-)
Example:
When this is finished, we end up with an image named like
businesscentral/insider:sandbox-17.0.15311.0-de
When this is finished, we end up with an image named like
businesscentral/insider:latest
Additional context
does it happen all the time? Reproducable every time.
did it use to work? No