* feat: remove unnecessary steps from prod pipeline, check they passed on staging in the prod aws deploy step instead
* feat: test condition
* Revert "feat: test condition"
This reverts commit 4146b2664b.
* CLDC-2812: update app config to run from relative root
* Deploy to staging on pushes to branch
* Add action mailer relative root config for review envs
* Temporary pipeline to deploy this branch for testing
* Update aws deploy pipeline to allow different prefixes for roles and tasks
* Prepare database when deploying review apps
* Update app nav and sentry to take account of relative root
* Update more fixed paths
* Update header root link path
* Rack attack path
* Revert "Deploy to staging on pushes to branch"
This reverts commit b05f13d474.
* Start updating workflows
* Update teardown pipeline to drop database
* Ensure destroy infra step runs after drop database
* Remove user_password_path because it can't be found
* Don't override path helpers in navigation items helper tests
* Checkout infra code to run workflow
* Try separating workflow call to job
* Sync with infra repo updates
* Use workflow on dev
* Don't trigger on push to branch
* Avoid rack attack path helper issue
* Update review apps teardown pipeline
* Update infra repo reference to main
* Fix linting
* Fix /logs redirect
* Fix lettings_logs_current and sales_logs_current checks in navigation items helper
* Fix existing bug in schemes nav item highlighting
* Use starts with rather than == in logs nav items current checks
* Split off non-support schemes current nav item checks
---------
Co-authored-by: Sam Seed <sam.seed@softwire.com>
* CLDC-2864: duplicate prod pipeline
* CLDC-2864: don't trigger aws pipeline
* CLDC-2864: turn off running on release (temporarily)
* CLDC-2864: switch to staging pipeline instead (as base to work from)
* CLDC-2864: only trigger manually
* CLDC-2864: change name of pipeline
* CLDC-2864: remove restriction that deploy only happens on main
* CLDC-2864: switch params to production from staging
* CLDC-2864: don't set API_USER and API_KEY
* CLDC-2863: remove 180s timeout for cf push command
* CLDC-2563: Update prod deployment pipeline
* CLDC-2563: remove redundant REPO_URL assignment
* CLDC-2563: use GITHUB_OUTPUT only where necessary
* CLDC-2563: don't push image if tag already exists
* CLDC-2563: actually use github.sha for production as well
* CLDC-2563: remove obsolete env check in push docker image job
* CLDC-2563: remove redundant main branch check
* CLDC-2565: Push docker images to AWS in staging pipeline
* CLDC-2711: Update based on changed resource names
* CLDC-2730: Update aws_deploy pipeline to run database migrations
* CLDC-2730: Temporarily run aws_deploy on push to this branch
* CLDC-2730: Update parameterisation
* CLDC-2730: Remove logging used for debugging
* CLDC-2731: Deploy application to aws
* CLDC-2731: Wait for service stability on deploy
* Revert "CLDC-2730: Temporarily run aws_deploy on push to this branch"
This reverts commit 8b4904dc7d.
* CLDC-2768: Sidekiq (AWS) (#1899)
* feat: update pipeline to deploy sidekiq to aws
* feat: update cron schedule to every 5mins temporarily
* feat: temporarily run aws_deploy on push to this branch
* feat: update aws ecs service name in pipeline
* Revert "feat: update cron schedule to every 5mins temporarily"
This reverts commit 80d0ab8383fa18e2bacd9ca0fa1a1d4048ef4f10.
* Revert "feat: temporarily run aws_deploy on push to this branch"
This reverts commit 48651712e6.
* style: remove unrequired empty line
* feat: reorder pipeline and update sidekiq task definition variable
---------
Co-authored-by: Chirag-Bhatti <109098469+Chirag-Bhatti@users.noreply.github.com>
* Update govuk-prototype-components
* Update node version
* Udate versions in the pipeline
* Do not fix to a specific buildpack version
* Update ruby version
* Upgrade govuk-frontend
* Update summary cards to use govuk frontend component
# Context
- We are mixing environments for review apps at the moment with staging
- As a result of this change bulk upload now works will CSV download
# Changes
- Created a new environment `dev` to store dev specific variables independent of staging
- Review apps now use this particular set of variables rather than the staging set
* update seeds to add self in review env, change spec to reflect this, update config yml to allow csv exports in review
* update interface of relevant methods
EmailCsvJob, LettingsLog.to_csv and LettingsLogCsvService consume codes_only flag
* update tests including adding a new csv file to test against
* update LettingsLogCsvService to output codes only csv
* correct minor error and linting
* enable codes only download in UI
- add link on lettings log index page
- pass codes_only flag through params in relevant links and methods
- convert flag to boolean in controller methods
* ensure link displayed successfully for all renderings of logs_list and params passed through relevant methods in organisations controller
* fix existing tests
* correct linting thing
* correct linting error
* update tests for lettings log controller
* correct linting errors
* update organisations controller tests
* make minor changes after code review
* remove changes made for testing on review app
* make codes only download visible to support users only
* change variable names throughout after info on rauby/rails naming conventions, update tests for change in who can view codes only download link
* rework csv service for readability, remove delegating methods from lettings log to keep all code to do with mapping between our domain and desired export format in one place
* update test name
* correct a small typo and remove a duplicated method after clever git merge conflict suggestion
* point review app at staging csv bucket for csv download
* change variables named codes_only_export to codes_only to avoid inconsistency
* write tests to ensure that differetn user roles have the correct permissions around csv download
* ensure that non support users may not download codes only exports
* correct a small error in a previous commit
* correct minor linting error
* Schedule data export tasks in sidekiq-cron
- Split combined XML and CSV data jobs into seperate background jobs
- Add sidekiq-cron to the project
- Schedule new XML and CSV jobs to run every day at 5am
- Adjust data export Rake tasks to use new job
* Add specs for DataExport{Xml,Csv}Job
* x
* Run bundle install
* Change review app export bucket name
---------
Co-authored-by: Kat <katrina@kosiak.co.uk>
- the following error seems to occur fairly frequently
```
Cannot cancel a deployment with status: FINALIZED and reason: DEGENERATE
```
- removing rolling deployments to see if this can resolve that
- I don't feel rolling deployments will be missed from review apps
* add start of bulk upload logs journey
* split upload controller into 2
* add year page to bulk upload journey
* bulk upload years now dynamic
* add placeholder for upload your file page
* handle bulk upload when not in crossover
* add bulk upload csv user journey
* bulk upload now persists and sends to S3
* swap ruby-filemagic for file command
* match csv or text file for validation
* in_crossover_period? now uses overlap of forms
- also moved from Form to FormHandler
* add production env var for CSV bucket
* stub kernel call methods
* remove duplicate env var
* hardcode env var for review apps
* move feature toggle to FeatureToggle
* crossover period checks now specific to the form
* fix typo in bulk upload journey
- there seems to be a race condition without this and there is a chance
not command will fail as it needs to wait for any existing operations
to complete first
* Replaced log CSV direct download with email
* Tidy up authorization of organisations controller
- We already have a method to authenticate the scope of the user, so we can reuse that.
* Use Rails routes instead of absolute paths for CSV download links
* Introduce base NotifyMailer to to abstract away shared Notify mail functionality
* Fix mailer spec name
* Add worker instance to PaaS manifest
* Add CSV download bucket instance name into environment
* Update tests for improved search term handling
* Fix download mailer tests
* Clarifying comments
Co-authored-by: natdeanlewissoftwire <nat.dean-lewis@softwire.com>
Co-authored-by: James Rose <james@jbpr.net>
natdeanlewissoftwire
kosiakkatrina
Rachael Booth
Chirag-Bhatti
SamSeed-Softwire
Phil Lee
Jack
Arthur Campbell
James Rose
natdeanlewissoftwire
Sam
Dushan
baarkerlounger
J G
Paul Robert Lloyd
baarkerlounger