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.

Sign up for GitHub

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

Jump to bottom

How do we handle updates? #35

Open
alranel opened this issue Jan 29, 2019 · 3 comments
Open

How do we handle updates? #35

alranel opened this issue Jan 29, 2019 · 3 comments
Labels
question Further information is requested

Comments

@alranel
Copy link
Member

alranel commented Jan 29, 2019

How can an administration check the current whitelist?
How can an administration update it?
Are multiple repos/orgs supported for a single administration?
@libremente libremente added the question Further information is requested label Jan 31, 2019
@libremente libremente mentioned this issue Jan 31, 2019
Merged
libremente added a commit that referenced this issue Feb 7, 2019
@libremente
feat: add deployment configuration (#37)
23ee56e 
* feat: added circleci lint and tests, added .eslintignore #32
* fix: changed config file name, added README info #35 #31
* feat: added gitignore info 
* fix: bump package.json to new versions due to security issues #29
@libremente
Copy link
Member

libremente commented Feb 7, 2019 •
edited
Loading

Info inserted in README, see #37

@alranel alranel reopened this Feb 26, 2019
@libremente
Copy link
Member

libremente commented Apr 9, 2019 •
edited
Loading

How can an administration check the current whitelist?

Navigate to /repo-list to see the current general whitelist. For what concerns the orgs belonging to an ipa, a dedicated issue has been opened #49.

How can an administration update it?

Dedicated issue opened #50.

Are multiple repos/orgs supported for a single administration?

At the moment of writing yes, they are, since the whitelist.db.json is not checked.
I'd close this issue.

@alranel
Copy link
Member Author

alranel commented May 27, 2019

L’onboarding prevederà la possibilità di aggiornare le informazioni attuali di un ente: organizzazioni e repository (aggiunta/rimozione), logo, URL sito web.

Flusso:

  • l’utente seleziona la sua amministrazione (ente/ufficio) dal dropdown (come ora)
    tutti i campi vengono popolati con le informazioni presenti in repo-list (tranne la PEC che viene sempre presa aggiornata da IndicePA e tranne il nome del referente che rimane vuoto perché va sempre compilato sul momento)
  • l’invio del form chiede conferma via PEC includendo tutte le informazioni (logo incluso, se possibile)
    a conferma avvenuta sovrascriviamo tutte le informazioni precedenti

Modifiche all’onboarding:

  • usiamo per repo-list lo stesso formato che usiamo nelle whitelist del crawler

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alranel @libremente