[FOLIO-2372] Move `dev.folio.org` to the FOLIO AWS Organization account Created: 30/Nov/19 Updated: 03/Jun/20 Resolved: 01/Dec/19 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | TBD |
| Reporter: | Peter Murray | Assignee: | Peter Murray |
| Resolution: | Done | Votes: | 0 |
| Labels: | devdoc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: |
| Description |
|
Corresponds to https://openlibraryenvironment.atlassian.net/browse/INFRA-7 |
| Comments |
| Comment by Peter Murray [ 30/Nov/19 ] |
|
Moved `rancher.dev.folio.org` CNAME for `rancher-bcdbc7ff7a0b3e30.elb.us-east-2.amazonaws.com` to `folio-org` organization. DNS entries for `dev.folio.org` updated at GoDaddy. Deleted stack on `kuali-ole`. Creation of stack on `folio-org` is stalled. Troubleshooting. |
| Comment by Peter Murray [ 01/Dec/19 ] |
|
Huh – there was also a misconfiguration in the CloudFront definition. To be honest, I'm not sure why this was working before, but it any case it is addressed now. Also fixed a problem where the Lambda would fail to report back an error to GitHub when the CodeBuild failed. |