rimbot test

Question

rimbot test

hougasian opened this issue 2 years ago · comments

Kevin Hougasian commented 2 years ago

rimbot testing
@mrtrimble @eridolfi12

rimdev-bot commented 2 years ago

platform

Kevin Hougasian · Answer 1 · Thu Feb 10 2022 02:27:52 GMT+0800 (China Standard Time)

@RIMBOT help

rimdev-bot · Answer 2 · Thu Feb 10 2022 02:27:54 GMT+0800 (China Standard Time)

Commands

@RIMBOT apps: Retrieves all the app ids rimbot knows about.
@RIMBOT azure [applicationIds]: Displays links to the Azure dashboard to diagnose deployment issues.
@RIMBOT azure-locks [-list -apply -remove]: Runs nightly to apply locks on resources in the Azure portal, with the goal of preventing deletion by Terraform. All locks are set nightly. They must be manually removed.
@RIMBOT clean-rimbot-state (-remove [appIds]) (-plan): Detects when an application is deleted from our system. Helps to remove the resource so RIMBOT state can be kept-up-to-date.
@RIMBOT debt: Provides debt report displaying commit difference between production and master.
@RIMBOT errors [applicationIds]: Gets error information from Application Insights.
@RIMBOT feature-flag [jobname] (-list/-toggle): List, enables, or disables RIMBOT jobs that run automatically.
@RIMBOT hangfire-audit: Audits Hangfire instances in all three environments.
@RIMBOT health [applicationIds]: Check the health of different applications and endpoints.
@RIMBOT help (command name): Get help with different RIMBOT commands. You can pass help a command name to get detailed help.
@RIMBOT infrastructure-reset: Runs infrastructure build to bring environment into alignment with terraform scripts. Runs every weekday morning to scale up development.
@RIMBOT log: Pulls the last 14 days of actions related to environment changes for all repositories.
@RIMBOT permissions-audit: Compares and audits permissions across different environments.
@RIMBOT prune-branches [applicationIds]: Deletes all release branches that are older than 30 days.
@RIMBOT redis-flush (-development/-staging/-production): Deletes all data out of Redis and can be used when resetting Auth. Requires one environment flag.
@RIMBOT refresh-database (-development/-staging): Copies database backup to development or staging.
@RIMBOT release [applicationIds]: Cuts a release branch off of master. Displays branch and commit information. When the release branch is cut, changes are deployed to staging.
@RIMBOT repave [applicationIds]: Repaves staging with production in an effort to make staging equal to the latest deployment.
@RIMBOT restart [applicationIds] (-development/-staging/-production) (-east/-west/-south): Initiates a restart for all servers in a cluster for an application unless a region flag is passed. Environment flag required.
@RIMBOT restart-all (-development/-staging/-production): Initiates a restart for ALL servers in the environment. Environment flag required.
@RIMBOT scale-down-dev: Scales down development during nights and weekends. Can only be used by rimbot.
@RIMBOT slot-diff: Checks to see if prod and staging have different code deployed for every app.
@RIMBOT swap [applicationIds] (-force): Swaps staging and production to deploy new changes.
@RIMBOT task [applicationIds] (-before/-after/-report): Allows users to tag commits, pull requests, and issues with important tasks to be completed before or after deployments.
@RIMBOT task-test [applicationIds] (-before/-after/-report): Allows users to tag commits, pull requests, and issues with important tasks to be completed before or after deployments.
@RIMBOT version [applicationIds]: Provides a summary of hashes for master and staging, as well as the last commit in production. Compare hashes are included.

Kevin Hougasian · Answer 3 · Thu Feb 10 2022 02:40:06 GMT+0800 (China Standard Time)

@RIMBOT help

rimdev-bot · Answer 4 · Thu Feb 10 2022 02:40:07 GMT+0800 (China Standard Time)

Commands

@RIMBOT apps: Retrieves all the app ids rimbot knows about.
@RIMBOT azure [applicationIds]: Displays links to the Azure dashboard to diagnose deployment issues.
@RIMBOT azure-locks [-list -apply -remove]: Runs nightly to apply locks on resources in the Azure portal, with the goal of preventing deletion by Terraform. All locks are set nightly. They must be manually removed.
@RIMBOT clean-rimbot-state (-remove [appIds]) (-plan): Detects when an application is deleted from our system. Helps to remove the resource so RIMBOT state can be kept-up-to-date.
@RIMBOT debt: Provides debt report displaying commit difference between production and master.
@RIMBOT errors [applicationIds]: Gets error information from Application Insights.
@RIMBOT feature-flag [jobname] (-list/-toggle): List, enables, or disables RIMBOT jobs that run automatically.
@RIMBOT hangfire-audit: Audits Hangfire instances in all three environments.
@RIMBOT health [applicationIds]: Check the health of different applications and endpoints.
@RIMBOT help (command name): Get help with different RIMBOT commands. You can pass help a command name to get detailed help.
@RIMBOT infrastructure-reset: Runs infrastructure build to bring environment into alignment with terraform scripts. Runs every weekday morning to scale up development.
@RIMBOT log: Pulls the last 14 days of actions related to environment changes for all repositories.
@RIMBOT permissions-audit: Compares and audits permissions across different environments.
@RIMBOT prune-branches [applicationIds]: Deletes all release branches that are older than 30 days.
@RIMBOT redis-flush (-development/-staging/-production): Deletes all data out of Redis and can be used when resetting Auth. Requires one environment flag.
@RIMBOT refresh-database (-development/-staging): Copies database backup to development or staging.
@RIMBOT release [applicationIds]: Cuts a release branch off of master. Displays branch and commit information. When the release branch is cut, changes are deployed to staging.
@RIMBOT repave [applicationIds]: Repaves staging with production in an effort to make staging equal to the latest deployment.
@RIMBOT restart [applicationIds] (-development/-staging/-production) (-east/-west/-south): Initiates a restart for all servers in a cluster for an application unless a region flag is passed. Environment flag required.
@RIMBOT restart-all (-development/-staging/-production): Initiates a restart for ALL servers in the environment. Environment flag required.
@RIMBOT scale-down-dev: Scales down development during nights and weekends. Can only be used by rimbot.
@RIMBOT slot-diff: Checks to see if prod and staging have different code deployed for every app.
@RIMBOT swap [applicationIds] (-force): Swaps staging and production to deploy new changes.
@RIMBOT task [applicationIds] (-before/-after/-report): Allows users to tag commits, pull requests, and issues with important tasks to be completed before or after deployments.
@RIMBOT task-test [applicationIds] (-before/-after/-report): Allows users to tag commits, pull requests, and issues with important tasks to be completed before or after deployments.
@RIMBOT version [applicationIds]: Provides a summary of hashes for master and staging, as well as the last commit in production. Compare hashes are included.

eridolfi12 · Answer 5 · Thu Feb 10 2022 03:36:55 GMT+0800 (China Standard Time)

@RIMBOT apps

rimdev-bot · Answer 6 · Thu Feb 10 2022 03:36:58 GMT+0800 (China Standard Time)

These are the available appIds:

accounts (-dev)
attachments-api (-dev)
auth (-dev)
auth-idsrv5-dev
auth-idsrv5-sample-dev
content-search (-dev)
contracting-api (-dev)
contracts (-dev)
crm-api (-dev)
docs (-dev)
docs-whitelabel (-dev)
idsrv5-accounts-dev
idsrv5-attachments-api-dev
idsrv5-contracting-api-dev
idsrv5-crm-api-dev
idsrv5-docs-dev
idsrv5-docs-whitelabel-dev
idsrv5-medicareful-dev
idsrv5-platform-dev
idsrv5-submissions-api-dev
medicareful (-dev)
medicareful-learn (-dev)
medicareful-learn-hugo-dev
medicareful-link (-dev)
medicareful-living-redesign-dev
medicareful-preview
platform (-dev)
platform-contract-support (-dev)
platform-ui-dev
quoteengine-api (-dev)
quoteengine-api-admin-dev
rimbot
ritterim (-dev)
sba-dev
school (-dev)
service-requests (-dev)
shield-dev
submissions-api (-dev)
terraform-test-application-dev
tide (-dev)

eridolfi12 · Answer 7 · Fri Feb 11 2022 02:09:04 GMT+0800 (China Standard Time)

@RIMBOT health platform (-dev)

rimdev-bot · Answer 8 · Fri Feb 11 2022 02:09:06 GMT+0800 (China Standard Time)

There was a problem with your health command. ["(-dev)"] are not valid application IDs. Valid application IDs are:

accounts (-dev)
attachments-api (-dev)
auth (-dev)
auth-idsrv5-dev
auth-idsrv5-sample-dev
content-search (-dev)
contracting-api (-dev)
contracts (-dev)
crm-api (-dev)
docs (-dev)
docs-whitelabel (-dev)
idsrv5-accounts-dev
idsrv5-attachments-api-dev
idsrv5-contracting-api-dev
idsrv5-crm-api-dev
idsrv5-docs-dev
idsrv5-docs-whitelabel-dev
idsrv5-medicareful-dev
idsrv5-platform-dev
idsrv5-submissions-api-dev
medicareful (-dev)
medicareful-learn (-dev)
medicareful-learn-hugo-dev
medicareful-link (-dev)
medicareful-living-redesign-dev
medicareful-preview
platform (-dev)
platform-contract-support (-dev)
platform-ui-dev
quoteengine-api (-dev)
quoteengine-api-admin-dev
rimbot
ritterim (-dev)
sba (-dev)
school (-dev)
service-requests (-dev)
shield-dev
submissions-api (-dev)
terraform-test-application-dev
tide (-dev)
You can also use the command @rimbot health all to check on all services

eridolfi12 · Answer 9 · Fri Feb 11 2022 02:09:52 GMT+0800 (China Standard Time)

@RIMBOT health platform

rimdev-bot · Answer 10 · Fri Feb 11 2022 02:09:53 GMT+0800 (China Standard Time)

Healthy Apps

platform

eridolfi12 · Answer 11 · Fri Feb 11 2022 03:19:01 GMT+0800 (China Standard Time)

@RIMBOT azure platform

eridolfi12 · Answer 12 · Fri Feb 11 2022 03:19:56 GMT+0800 (China Standard Time)

@RIMBOT apps

rimdev-bot · Answer 13 · Fri Feb 11 2022 03:19:57 GMT+0800 (China Standard Time)

These are the available appIds:

accounts (-dev)
attachments-api (-dev)
auth (-dev)
auth-idsrv5-dev
auth-idsrv5-sample-dev
content-search (-dev)
contracting-api (-dev)
contracts (-dev)
crm-api (-dev)
docs (-dev)
docs-whitelabel (-dev)
idsrv5-accounts-dev
idsrv5-attachments-api-dev
idsrv5-contracting-api-dev
idsrv5-crm-api-dev
idsrv5-docs-dev
idsrv5-docs-whitelabel-dev
idsrv5-medicareful-dev
idsrv5-platform-dev
idsrv5-submissions-api-dev
medicareful (-dev)
medicareful-learn (-dev)
medicareful-learn-hugo-dev
medicareful-link (-dev)
medicareful-living-redesign-dev
medicareful-preview
platform (-dev)
platform-contract-support (-dev)
platform-ui-dev
quoteengine-api (-dev)
quoteengine-api-admin-dev
rimbot
ritterim (-dev)
sba (-dev)
school (-dev)
service-requests (-dev)
shield-dev
submissions-api (-dev)
terraform-test-application-dev
tide (-dev)

eridolfi12 · Answer 14 · Fri Feb 11 2022 03:20:42 GMT+0800 (China Standard Time)

@RIMBOT azure submission-api

rimdev-bot · Answer 15 · Fri Feb 11 2022 03:20:43 GMT+0800 (China Standard Time)

There was a problem with your azure command. ["submission-api"] are not valid application IDs. Valid application IDs are:

accounts (-dev)
attachments-api (-dev)
auth (-dev)
auth-idsrv5-dev
auth-idsrv5-sample-dev
content-search (-dev)
contracting-api (-dev)
contracts (-dev)
crm-api (-dev)
docs (-dev)
docs-whitelabel (-dev)
idsrv5-accounts-dev
idsrv5-attachments-api-dev
idsrv5-contracting-api-dev
idsrv5-crm-api-dev
idsrv5-docs-dev
idsrv5-docs-whitelabel-dev
idsrv5-medicareful-dev
idsrv5-platform-dev
idsrv5-submissions-api-dev
medicareful (-dev)
medicareful-learn (-dev)
medicareful-learn-hugo-dev
medicareful-link (-dev)
medicareful-living-redesign-dev
medicareful-preview
platform (-dev)
platform-contract-support (-dev)
platform-ui-dev
quoteengine-api (-dev)
quoteengine-api-admin-dev
rimbot
ritterim (-dev)
sba (-dev)
school (-dev)
service-requests (-dev)
shield-dev
submissions-api (-dev)
terraform-test-application-dev
tide (-dev)