You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With New-IcingaRepository is it possible to create own repositories. But they are always defined as "stable" repo. There is no switch available to say the cmdlet that the new repo is a snapshot repo. You can only edit the new json file. But with the Sync-IcingaRepository it is again a stable repo.
This would be important if we want to use - e.g. for test environment - the snapshot repos. And as default behavior and for security reasons our servers have no access to the internet.
Especially for a test and development environment a staging is very usful. If this would be possible, We could use also the param -Snapshot with every other existing repo cmcllet.
As workarround we created diffrent "stable"-repos. And depending on the kind of server, we assign and activate the repo. A bit cumbersome, but it's possible.
The text was updated successfully, but these errors were encountered:
With
New-IcingaRepository
is it possible to create own repositories. But they are always defined as "stable" repo. There is no switch available to say the cmdlet that the new repo is a snapshot repo. You can only edit the new json file. But with theSync-IcingaRepository
it is again a stable repo.This would be important if we want to use - e.g. for test environment - the snapshot repos. And as default behavior and for security reasons our servers have no access to the internet.
Especially for a test and development environment a staging is very usful. If this would be possible, We could use also the param -Snapshot with every other existing repo cmcllet.
As workarround we created diffrent "stable"-repos. And depending on the kind of server, we assign and activate the repo. A bit cumbersome, but it's possible.
The text was updated successfully, but these errors were encountered: