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 contact information to Swagger UI (#6205) #6720

Open
wants to merge 4 commits into
base: develop
Choose a base branch
from

Conversation

achave11-ucsc
Copy link
Member

@achave11-ucsc achave11-ucsc commented Nov 20, 2024

Connected issues: #6205

Checklist

Author

  • PR is a draft
  • Target branch is develop
  • Name of PR branch matches issues/<GitHub handle of author>/<issue#>-<slug>
  • On ZenHub, PR is connected to all issues it (partially) resolves
  • PR description links to connected issues
  • PR title matches1 that of a connected issue or comment in PR explains why they're different
  • PR title references all connected issues
  • For each connected issue, there is at least one commit whose title references that issue

1 when the issue title describes a problem, the corresponding PR
title is Fix: followed by the issue title

Author (partiality)

  • Added p tag to titles of partial commits
  • This PR is labeled partial or completely resolves all connected issues
  • This PR partially resolves each of the connected issues or does not have the partial label

Author (chains)

  • This PR is blocked by previous PR in the chain or is not chained to another PR
  • The blocking PR is labeled base or this PR is not chained to another PR
  • This PR is labeled chained or is not chained to another PR

Author (reindex, API changes)

  • Added r tag to commit title or the changes introduced by this PR will not require reindexing of any deployment
  • This PR is labeled reindex:dev or the changes introduced by it will not require reindexing of dev
  • This PR is labeled reindex:anvildev or the changes introduced by it will not require reindexing of anvildev
  • This PR is labeled reindex:anvilprod or the changes introduced by it will not require reindexing of anvilprod
  • This PR is labeled reindex:prod or the changes introduced by it will not require reindexing of prod
  • This PR is labeled reindex:partial and its description documents the specific reindexing procedure for dev, anvildev, anvilprod and prod or requires a full reindex or carries none of the labels reindex:dev, reindex:anvildev, reindex:anvilprod and reindex:prod
  • This PR and its connected issues are labeled API or this PR does not modify a REST API
  • Added a (A) tag to commit title for backwards (in)compatible changes or this PR does not modify a REST API
  • Updated REST API version number in app.py or this PR does not modify a REST API

Author (upgrading deployments)

  • Ran make docker_images.json and committed the resulting changes or this PR does not modify azul_docker_images, or any other variables referenced in the definition of that variable
  • Documented upgrading of deployments in UPGRADING.rst or this PR does not require upgrading deployments
  • Added u tag to commit title or this PR does not require upgrading deployments
  • This PR is labeled upgrade or does not require upgrading deployments
  • This PR is labeled deploy:shared or does not modify docker_images.json, and does not require deploying the shared component for any other reason
  • This PR is labeled deploy:gitlab or does not require deploying the gitlab component
  • This PR is labeled deploy:runner or does not require deploying the runner image

Author (hotfixes)

  • Added F tag to main commit title or this PR does not include permanent fix for a temporary hotfix
  • Reverted the temporary hotfixes for any connected issues or the none of the stable branches (anvilprod and prod) have temporary hotfixes for any of the issues connected to this PR

Author (before every review)

  • Rebased PR branch on develop, squashed old fixups
  • Ran make requirements_update or this PR does not modify requirements*.txt, common.mk, Makefile and Dockerfile
  • Added R tag to commit title or this PR does not modify requirements*.txt
  • This PR is labeled reqs or does not modify requirements*.txt
  • make integration_test passes in personal deployment or this PR does not modify functionality that could affect the IT outcome

Peer reviewer (after approval)

  • PR is not a draft
  • Ticket is in Review requested column
  • PR is awaiting requested review from system administrator
  • PR is assigned to only the system administrator

System administrator (after approval)

  • Actually approved the PR
  • Labeled connected issues as demo or no demo
  • Commented on connected issues about demo expectations or all connected issues are labeled no demo
  • Decided if PR can be labeled no sandbox
  • A comment to this PR details the completed security design review
  • PR title is appropriate as title of merge commit
  • N reviews label is accurate
  • Moved connected issues to Approved column
  • PR is assigned to only the operator

Operator (before pushing merge the commit)

  • Checked reindex:… labels and r commit title tag
  • Checked that demo expectations are clear or all connected issues are labeled no demo
  • Squashed PR branch and rebased onto develop
  • Sanity-checked history
  • Pushed PR branch to GitHub
  • Ran _select dev.shared && CI_COMMIT_REF_NAME=develop make -C terraform/shared apply_keep_unused or this PR is not labeled deploy:shared
  • Ran _select dev.gitlab && CI_COMMIT_REF_NAME=develop make -C terraform/gitlab apply or this PR is not labeled deploy:gitlab
  • Ran _select anvildev.shared && CI_COMMIT_REF_NAME=develop make -C terraform/shared apply_keep_unused or this PR is not labeled deploy:shared
  • Ran _select anvildev.gitlab && CI_COMMIT_REF_NAME=develop make -C terraform/gitlab apply or this PR is not labeled deploy:gitlab
  • Checked the items in the next section or this PR is labeled deploy:gitlab
  • PR is assigned to only the system administrator or this PR is not labeled deploy:gitlab

System administrator

  • Background migrations for dev.gitlab are complete or this PR is not labeled deploy:gitlab
  • Background migrations for anvildev.gitlab are complete or this PR is not labeled deploy:gitlab
  • PR is assigned to only the operator

Operator (before pushing merge the commit)

  • Ran _select dev.gitlab && make -C terraform/gitlab/runner or this PR is not labeled deploy:runner
  • Ran _select anvildev.gitlab && make -C terraform/gitlab/runner or this PR is not labeled deploy:runner
  • Added sandbox label or PR is labeled no sandbox
  • Pushed PR branch to GitLab dev or PR is labeled no sandbox
  • Pushed PR branch to GitLab anvildev or PR is labeled no sandbox
  • Build passes in sandbox deployment or PR is labeled no sandbox
  • Build passes in anvilbox deployment or PR is labeled no sandbox
  • Reviewed build logs for anomalies in sandbox deployment or PR is labeled no sandbox
  • Reviewed build logs for anomalies in anvilbox deployment or PR is labeled no sandbox
  • Deleted unreferenced indices in sandbox or this PR does not remove catalogs or otherwise causes unreferenced indices in dev
  • Deleted unreferenced indices in anvilbox or this PR does not remove catalogs or otherwise causes unreferenced indices in anvildev
  • Started reindex in sandbox or this PR is not labeled reindex:dev
  • Started reindex in anvilbox or this PR is not labeled reindex:anvildev
  • Checked for failures in sandbox or this PR is not labeled reindex:dev
  • Checked for failures in anvilbox or this PR is not labeled reindex:anvildev
  • The title of the merge commit starts with the title of this PR
  • Added PR # reference to merge commit title
  • Collected commit title tags in merge commit title but only included p if the PR is also labeled partial
  • Moved connected issues to Merged lower column in ZenHub
  • Moved blocked issues to Triage or no issues are blocked on the connected issues
  • Pushed merge commit to GitHub

Operator (chain shortening)

  • Changed the target branch of the blocked PR to develop or this PR is not labeled base
  • Removed the chained label from the blocked PR or this PR is not labeled base
  • Removed the blocking relationship from the blocked PR or this PR is not labeled base
  • Removed the base label from this PR or this PR is not labeled base

Operator (after pushing the merge commit)

  • Pushed merge commit to GitLab dev
  • Pushed merge commit to GitLab anvildev
  • Build passes on GitLab dev
  • Reviewed build logs for anomalies on GitLab dev
  • Build passes on GitLab anvildev
  • Reviewed build logs for anomalies on GitLab anvildev
  • Ran _select dev.shared && make -C terraform/shared apply or this PR is not labeled deploy:shared
  • Ran _select anvildev.shared && make -C terraform/shared apply or this PR is not labeled deploy:shared
  • Deleted PR branch from GitHub
  • Deleted PR branch from GitLab dev
  • Deleted PR branch from GitLab anvildev

Operator (reindex)

  • Deindexed all unreferenced catalogs in dev or this PR is neither labeled reindex:partial nor reindex:dev
  • Deindexed all unreferenced catalogs in anvildev or this PR is neither labeled reindex:partial nor reindex:anvildev
  • Deindexed specific sources in dev or this PR is neither labeled reindex:partial nor reindex:dev
  • Deindexed specific sources in anvildev or this PR is neither labeled reindex:partial nor reindex:anvildev
  • Indexed specific sources in dev or this PR is neither labeled reindex:partial nor reindex:dev
  • Indexed specific sources in anvildev or this PR is neither labeled reindex:partial nor reindex:anvildev
  • Started reindex in dev or this PR does not require reindexing dev
  • Started reindex in anvildev or this PR does not require reindexing anvildev
  • Checked for, triaged and possibly requeued messages in both fail queues in dev or this PR does not require reindexing dev
  • Checked for, triaged and possibly requeued messages in both fail queues in anvildev or this PR does not require reindexing anvildev
  • Emptied fail queues in dev or this PR does not require reindexing dev
  • Emptied fail queues in anvildev or this PR does not require reindexing anvildev

Operator

  • Propagated the deploy:shared, deploy:gitlab, deploy:runner, API, reindex:partial, reindex:anvilprod and reindex:prod labels to the next promotion PRs or this PR carries none of these labels
  • Propagated any specific instructions related to the deploy:shared, deploy:gitlab, deploy:runner, API, reindex:partial, reindex:anvilprod and reindex:prod labels, from the description of this PR to that of the next promotion PRs or this PR carries none of these labels
  • PR is assigned to no one

Shorthand for review comments

  • L line is too long
  • W line wrapping is wrong
  • Q bad quotes
  • F other formatting problem

@github-actions github-actions bot added the orange [process] Done by the Azul team label Nov 20, 2024
@achave11-ucsc achave11-ucsc added the API API change affecting callers label Nov 20, 2024
@achave11-ucsc achave11-ucsc force-pushed the issues/achave11-ucsc/6205-add-contact-to-swagger branch from 176b1ed to 721a91a Compare November 20, 2024 17:58
Copy link

codecov bot commented Nov 20, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.68%. Comparing base (0bb6aab) to head (85066ce).

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #6720      +/-   ##
===========================================
+ Coverage    85.66%   85.68%   +0.01%     
===========================================
  Files          149      149              
  Lines        20996    21013      +17     
===========================================
+ Hits         17987    18005      +18     
+ Misses        3009     3008       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@coveralls
Copy link

coveralls commented Nov 20, 2024

Coverage Status

coverage: 85.702% (+0.02%) from 85.686%
when pulling 85066ce on issues/achave11-ucsc/6205-add-contact-to-swagger
into 0bb6aab on develop.

@achave11-ucsc achave11-ucsc force-pushed the issues/achave11-ucsc/6205-add-contact-to-swagger branch from 721a91a to 11a1181 Compare November 20, 2024 20:15
@achave11-ucsc achave11-ucsc removed the API API change affecting callers label Nov 20, 2024
[GitHub](https://github.com/DataBiosphere/azul/issues) or email
`[email protected]`. To report a security concern or misconduct
please email `[email protected]`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change

nadove-ucsc
nadove-ucsc previously approved these changes Nov 21, 2024
@nadove-ucsc nadove-ucsc marked this pull request as ready for review November 21, 2024 02:01
## Contact us
For technical and user support please file an issue on
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
For technical and user support please file an issue on
For technical support please file an issue at

Comment on lines 224 to 230
## Contact us
For technical and user support please file an issue on
[GitHub](https://github.com/DataBiosphere/azul/issues) or email
`[email protected]`. To report a security concern or misconduct
please email `[email protected]`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should be possible to avoid this duplication.

@hannes-ucsc hannes-ucsc removed their assignment Nov 26, 2024
@hannes-ucsc hannes-ucsc added the 1 review [process] Lead requested changes once label Nov 26, 2024
@achave11-ucsc achave11-ucsc force-pushed the issues/achave11-ucsc/6205-add-contact-to-swagger branch from d792aa0 to 9db9335 Compare November 26, 2024 19:27
@achave11-ucsc achave11-ucsc force-pushed the issues/achave11-ucsc/6205-add-contact-to-swagger branch 5 times, most recently from d2d5d3d to 552bcda Compare December 5, 2024 23:20
@hannes-ucsc hannes-ucsc removed their assignment Jan 13, 2025
@hannes-ucsc
Copy link
Member

Security design review

  • Security design review completed; this PR does not
    • … affect authentication; for example:
      • OAuth 2.0 with the application (API or Swagger UI)
      • Authentication of developers with Google Cloud APIs
      • Authentication of developers with AWS APIs
      • Authentication with a GitLab instance in the system
      • Password and 2FA authentication with GitHub
      • API access token authentication with GitHub
      • Authentication with Terra
    • … affect the permissions of internal users like access to
      • Cloud resources on AWS and GCP
      • GitLab repositories, projects and groups, administration
      • an EC2 instance via SSH
      • GitHub issues, pull requests, commits, commit statuses, wikis, repositories, organizations
    • … affect the permissions of external users like access to
      • TDR snapshots
    • … affect permissions of service or bot accounts
      • Cloud resources on AWS and GCP
    • … affect audit logging in the system, like
      • adding, removing or changing a log message that represents an auditable event
      • changing the routing of log messages through the system
    • … affect monitoring of the system
    • … introduce a new software dependency like
      • Python packages on PYPI
      • Command-line utilities
      • Docker images
      • Terraform providers
    • … add an interface that exposes sensitive or confidential data at the security boundary
    • … affect the encryption of data at rest
    • … require persistence of sensitive or confidential data that might require encryption at rest
    • … require unencrypted transmission of data within the security boundary
    • … affect the network security layer; for example by
      • modifying, adding or removing firewall rules
      • modifying, adding or removing security groups
      • changing or adding a port a service, proxy or load balancer listens on
  • Documentation on any unchecked boxes is provided in comments below

hannes-ucsc
hannes-ucsc previously approved these changes Jan 13, 2025
@hannes-ucsc hannes-ucsc removed the request for review from nadove-ucsc January 13, 2025 19:35
@achave11-ucsc achave11-ucsc force-pushed the issues/achave11-ucsc/6205-add-contact-to-swagger branch from 5a7f4c2 to 359edb9 Compare January 13, 2025 22:27
@achave11-ucsc achave11-ucsc added the sandbox [process] Resolution is being verified in sandbox deployment label Jan 13, 2025
@achave11-ucsc
Copy link
Member Author

PR failed sandbox, returning to in progress for further triaging.
https://gitlab.dev.singlecell.gi.ucsc.edu/ucsc/azul/-/jobs/108066
https://gitlab.anvil.gi.ucsc.edu/ucsc/azul/-/jobs/55734

@achave11-ucsc
Copy link
Member Author

The make check_clean target fails …

$ make check_clean
git diff --exit-code && git diff --cached --exit-code
diff --git a/lambdas/indexer/openapi.json b/lambdas/indexer/openapi.json
index 06738c6..3274d94 100644
--- a/lambdas/indexer/openapi.json
+++ b/lambdas/indexer/openapi.json
@@ -2,7 +2,7 @@
     "openapi": "3.0.1",
     "info": {
         "title": "azul-indexer-dev",
-        "description": "…CONDENSED… or email\n`[email protected]`. To report a security concern or misconduct please email\n`[email protected]`.\n",
+        "description": "…CONDENSED… or email\n`[email protected]`. To report a security concern or misconduct please email\n`[email protected]`.\n",
         "version": "1.1"
     },

… this is due to the sandbox deployments deriving the monitoring email from AZUL_OWNER, which in this case is [email protected].

diff --git a/deployments/anvilbox/environment.py b/deployments/anvilbox/environment.py
index f000d4380..a667e1c8b 100644
--- a/deployments/anvilbox/environment.py
+++ b/deployments/anvilbox/environment.py
@@ -150,6 +150,7 @@ def env() -> Mapping[str, Optional[str]]:
         'AZUL_OWNER': '[email protected]' if is_sandbox else None,
 
         'AZUL_MONITORING_EMAIL': '{AZUL_OWNER}',
+        # NOTE ^^
 
         'AZUL_AWS_ACCOUNT_ID': '289950828509',
         'AWS_DEFAULT_REGION': 'us-east-1',
diff --git a/deployments/hammerbox/environment.py b/deployments/hammerbox/environment.py
index 3265eacd9..af2771ce5 100644
--- a/deployments/hammerbox/environment.py
+++ b/deployments/hammerbox/environment.py
@@ -1026,6 +1026,7 @@ def env() -> Mapping[str, Optional[str]]:
         'AZUL_OWNER': '[email protected]' if is_sandbox else None,
 
         'AZUL_MONITORING_EMAIL': '{AZUL_OWNER}',
+        # NOTE ^^
 
         'AZUL_AWS_ACCOUNT_ID': '465330168186',
         'AWS_DEFAULT_REGION': 'us-east-1',
diff --git a/deployments/sandbox/environment.py b/deployments/sandbox/environment.py
index 7b0860f94..80ace3b83 100644
--- a/deployments/sandbox/environment.py
+++ b/deployments/sandbox/environment.py
@@ -273,6 +273,7 @@ def env() -> Mapping[str, Optional[str]]:
         'AZUL_OWNER': '[email protected]' if is_sandbox else None,
 
         'AZUL_MONITORING_EMAIL': '{AZUL_OWNER}',
+        # NOTE ^^
 
         'AZUL_AWS_ACCOUNT_ID': '122796619775',
         'AWS_DEFAULT_REGION': 'us-east-1',

When the OpenAPI spec is generated with this details, given …

   @property
    def contact_us(self) -> str:
        email = self.monitoring_email
        return format_description(f'''
            ## Contact us
            For technical support please file an issue at
            [GitHub](https://github.com/DataBiosphere/azul/issues) or email
            `{email}`. To report a security concern or misconduct please email
            `{email}`.
        ''')

… in src/azul/__init__.py from this PR, it results in the make check_clean failure.

@achave11-ucsc achave11-ucsc force-pushed the issues/achave11-ucsc/6205-add-contact-to-swagger branch 4 times, most recently from 144a3db to 06a9d7a Compare January 17, 2025 00:04
@achave11-ucsc achave11-ucsc removed their assignment Jan 17, 2025
@hannes-ucsc hannes-ucsc force-pushed the issues/achave11-ucsc/6205-add-contact-to-swagger branch from 06a9d7a to 1294e31 Compare January 17, 2025 23:31
hannes-ucsc
hannes-ucsc previously approved these changes Jan 17, 2025
Condense patching of config properties
@hannes-ucsc hannes-ucsc force-pushed the issues/achave11-ucsc/6205-add-contact-to-swagger branch from 1294e31 to 85066ce Compare January 17, 2025 23:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 reviews [process] Lead requested changes thrice orange [process] Done by the Azul team sandbox [process] Resolution is being verified in sandbox deployment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants