You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RC subsites make the same requests to RC API using the contract_id in some places and the open_contracting_id in other places. We should be consistent.
What
open_contracting_id is used everywhere where we are requesting data about a contract from RC-API
Hi @charlesyoung ,
This issue and #1176 were raised due to the outage caused by the migration of Elasticsearch. @anjesh and his team might be able to them faster than us because they are more familiar with how RC works, but we can also do them if needed.
This fixes should allow us to scale down Elasticsearch.
Why
RC subsites make the same requests to RC API using the
contract_id
in some places and theopen_contracting_id
in other places. We should be consistent.What
open_contracting_id
is used everywhere where we are requesting data about a contract from RC-APINotes
This is a follow up issue for #1172 .
The text was updated successfully, but these errors were encountered: