Skip to content

Add state check to verifyarchives helper and use to verify FINAL Archives only #267

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

Closed

Conversation

jonasbardino
Copy link
Contributor

Implement a simple -s STATE option in the verifyarchives.py helper to make it fail if the verified archive is not actually in STATE. Use it by default in the generated migverifyarchives cron job with -s FINAL, so that in case a non-FINAL archive should enter the list of archives to verify it will fail and tell why.

…ign better with secure-by-default considerations. In effect this reduces the set of enabled services unless explicitly requested. The examples in the README have been updated accordingly.

git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6067 b75ad72c-e7d7-11dd-a971-7dbc132099af
…der, adjusted long comment to fit line, removed pyoth from recommended.txt now that it's in required.txt and fix a couple of typos in comment.

git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6069 b75ad72c-e7d7-11dd-a971-7dbc132099af
git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6070 b75ad72c-e7d7-11dd-a971-7dbc132099af
git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6071 b75ad72c-e7d7-11dd-a971-7dbc132099af
git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6072 b75ad72c-e7d7-11dd-a971-7dbc132099af
…eaks some cases where migrid modules require sys.path mangling

git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6074 b75ad72c-e7d7-11dd-a971-7dbc132099af
git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6075 b75ad72c-e7d7-11dd-a971-7dbc132099af
…p8 import mangling

git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6076 b75ad72c-e7d7-11dd-a971-7dbc132099af
git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6077 b75ad72c-e7d7-11dd-a971-7dbc132099af
… up attempts. Both kind of OpenID sign up used to rely on the original configuration.auto_add_oid_user .

git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6078 b75ad72c-e7d7-11dd-a971-7dbc132099af
git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6079 b75ad72c-e7d7-11dd-a971-7dbc132099af
git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6080 b75ad72c-e7d7-11dd-a971-7dbc132099af
…rid where the 'somearg is keyword_auto' comparison in generateconfs fails, when passing the default 'AUTO' values e.g. for salts. This a.o. breaks the CI genoiddiscovery.py call because 'AUTO' ends up in the MiGserver.conf and causes havoc on parsing. Comparing the values with 'somearg == keyword_auto' instead solves the problems. Further analysis may be needed but perhaps it's due to string argument passing throught the command line or any mangling like somearg.upper() or the like that the memory address comparison with 'is' fails. In most other cases it makes no difference, which is used for comparing string literals.

git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6081 b75ad72c-e7d7-11dd-a971-7dbc132099af
git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6082 b75ad72c-e7d7-11dd-a971-7dbc132099af
git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6083 b75ad72c-e7d7-11dd-a971-7dbc132099af
git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6084 b75ad72c-e7d7-11dd-a971-7dbc132099af
git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6085 b75ad72c-e7d7-11dd-a971-7dbc132099af
git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6086 b75ad72c-e7d7-11dd-a971-7dbc132099af
git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6087 b75ad72c-e7d7-11dd-a971-7dbc132099af
git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6088 b75ad72c-e7d7-11dd-a971-7dbc132099af
git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6089 b75ad72c-e7d7-11dd-a971-7dbc132099af
…d I made a number of adjustments to document said conf options and put them in a slightly more 'logical' location and order, which I realized was not at all obvious for anyone but us few long-term operators.

git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6090 b75ad72c-e7d7-11dd-a971-7dbc132099af
…exists rather than if the path pointed to exists. Addresses a regression in edituser with the unique id symlinks not being properly removed in preparation for relinking it to the new X509 ID.

git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6091 b75ad72c-e7d7-11dd-a971-7dbc132099af
…nts and added missing docstrings on new generate helper functions.

git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6092 b75ad72c-e7d7-11dd-a971-7dbc132099af
git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6093 b75ad72c-e7d7-11dd-a971-7dbc132099af
… alias for migrid.org. Clean up stale system warnings

git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6094 b75ad72c-e7d7-11dd-a971-7dbc132099af
…ents on github: fixed a comment typo, a PEP8 style recommendation and rearranged a few lines for tighter clustering of related code lines.

git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6096 b75ad72c-e7d7-11dd-a971-7dbc132099af
Martin-Rehr and others added 24 commits May 13, 2025 15:10
git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6232 b75ad72c-e7d7-11dd-a971-7dbc132099af
…ave it filtered from released source archives through the .gitattributes file.

git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6233 b75ad72c-e7d7-11dd-a971-7dbc132099af
…re warning emails to point to the new built-in Renew button at the Account page where applicable in order to limit operator overhead from account renewals.

git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6234 b75ad72c-e7d7-11dd-a971-7dbc132099af
…ccessfully logging out from OIDC and all sessions.

git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6235 b75ad72c-e7d7-11dd-a971-7dbc132099af
git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6236 b75ad72c-e7d7-11dd-a971-7dbc132099af
…n MiGserver.conf which will load SECTIONNAME into parsed configuration for any sectionname.conf files from the corresponding folder. Useful e.g. to keep rather involved cloud sections out of the main MiGserver.conf

git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6237 b75ad72c-e7d7-11dd-a971-7dbc132099af
git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6238 b75ad72c-e7d7-11dd-a971-7dbc132099af
git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6239 b75ad72c-e7d7-11dd-a971-7dbc132099af
… in migerrors cronjob

git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6240 b75ad72c-e7d7-11dd-a971-7dbc132099af
…ssential GLOBAL and SITE conf options through include sections

git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6241 b75ad72c-e7d7-11dd-a971-7dbc132099af
git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6242 b75ad72c-e7d7-11dd-a971-7dbc132099af
…enid

git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6243 b75ad72c-e7d7-11dd-a971-7dbc132099af
git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6244 b75ad72c-e7d7-11dd-a971-7dbc132099af
git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6245 b75ad72c-e7d7-11dd-a971-7dbc132099af
…ps argument

git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6246 b75ad72c-e7d7-11dd-a971-7dbc132099af
…failing GH Actions on rocky8

git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6247 b75ad72c-e7d7-11dd-a971-7dbc132099af
…ly last svn action.

git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6248 b75ad72c-e7d7-11dd-a971-7dbc132099af
…o address

e.g. python sanity checks failing on Rocky8 due to missing enchant system lib.
… to python3 with future hosting at github.

git-svn-id: svn+ssh://svn.code.sf.net/p/migrid/code/trunk@6249 b75ad72c-e7d7-11dd-a971-7dbc132099af
@jonasbardino jonasbardino self-assigned this Jun 20, 2025
@jonasbardino jonasbardino added the enhancement New feature or request label Jun 20, 2025
…to make it

fail if the verified archive is not actually in `STATE`. Use it by default in
the generated `migverifyarchives` cron job with `-s FINAL`, so that in case a
non-FINAL archive should enter the list of archives to verify it will fail and
tell why.
@jonasbardino
Copy link
Contributor Author

Sigh, PR of next commit against edge causes a lot of noise. Retired and fixed in PR #268 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants