Skip to content
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 flags to bendini to decide what to do about version conflicts #133

Open
sakarias88 opened this issue Oct 14, 2020 · 0 comments
Open

Comments

@sakarias88
Copy link
Member

An example we have today when we deploy "new" functions where we first register and upload attachments before checking if we can actually register the function. This means we upload orphaned attachments just because function registry fails.

We must always check if the function exists but we need a flag to decide what to do in case it finds an already registered function.

Right now a duplicate counts as a function with same name and version. The code might still be different though. This flag is for deciding the strictness of the check. It could for example compare the checksums between the local version and the already uploaded version. Skip all duplicates, skip duplicates with matching checksum, skip no duplicates. --skip-duplicates all/matching-manifest/matching-checksum/none

@sakarias88 sakarias88 transferred this issue from another repository Oct 14, 2020
@simonrainerson simonrainerson changed the title Add flags to lomax to decide what to do about version conflicts Add flags to bendini to decide what to do about version conflicts Mar 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant