* Portal changes for DedicatedGateway
Changes to support creation and deletion of DedicatedGateway resource.
Tested locally with various scenarios.
* Portal changes for DedicatedGateway. CR feedback
* Stylecop changes
* created selfServe.html landing page
* Removing TODO comments
* exposed baselineValues
* added getOnSaveNotification
* disable UI when onSave is taking place
* minro edits
* made polling optional
* added optional polling
* added default
* Added portal notifications
* merged more changes
* minor edits
* added label for description
* Added correlationids and polling of refresh
* Added correlationids and polling of refresh
* minor edit
* added label tooltip
* removed ClassInfo decorator
* Added dynamic decription
* added info and warninf types for description
* more changes to promise retry
* promise retry changes
* added spinner on selfserve load
* compile errors fixed
* New changes
* added operationstatus link
* merged sqlxEdits
* undid sqlx changes
* added completed notification
* passed retryInterval in notif options
* more retry changes
* more changes
* added polling on landing on the page
* edits for error display
* added keys blade link
* added link generation
* added link to blade
* Modified info and description
* fixed format errors
* added selfserve contract to output files
* addressed PR comments
Co-authored-by: Balaji Sridharan <fnbalaji@microsoft.com>
Co-authored-by: fnbalaji <75445927+fnbalaji@users.noreply.github.com>
I got cold feet at the thought of merging #324 in one go, so I'm going to split it into smaller chunks and keep rebasing the large one until there's no more Q.
* added recursion and inition decorators
* working version
* added todo comment and removed console.log
* Added Recursive add
* removed type requirement
* proper resolution of promises
* added custom element and base class
* Made selfServe standalone page
* Added custom renderer as async type
* Added overall defaults
* added inital open from data explorer
* removed landingpage
* added feature for self serve type
* renamed sqlx->example and added invalid type
* Added comments for Example
* removed unnecessary changes
* Resolved PR comments
Added tests
Moved onSubmt and initialize inside base class
Moved testExplorer to separate folder
made fields of SelfServe Class non static
* fixed lint errors
* fixed compilation errors
* Removed reactbinding changes
* renamed dropdown -> choice
* Added SelfServeComponent
* Addressed PR comments
* merged master
* added selfservetype.none for emulator and hosted experience
* fixed formatting errors
* Removed "any" type
* undid package.json changes
* Adding autoscale flight info
* Add flight info to cassandra collection pane
* Add telemetry for autoscale toggle on/off in create resource blade and scale/settings
* Run formatting and add expected properties to test file
* removing empty line
* Updating to pass unit tests
Co-authored-by: Steve Faulkner <southpolesteve@gmail.com>
* Initial change of estimated cost to table format
* Converted cost estimate to table format and added different data for current vs updated cost estimates.
* lint fixes
* Changed the names of some interfaces
* Refactored a unit call to use an argument interface to avoid future confusion.
* Changed the severity of the save warning
* Format fix
* Fixed test due to styling change
Co-authored-by: Steve Faulkner <southpolesteve@gmail.com>
- Removed `readCollectionQuotaInfo` call. The only data we need is the usage size which we can get via the ARM metrics call instead.
- Added `getCollectionUsageSize` which fetches the `DataUsage` and `IndexUsage` metrics, converts them to KB, and returns the sum as the total usage size
- Make sure we pass the error message string instead of an error object when we call `TelemetryProcessor.traceFailure` since TelemetryProcessor will call `JSON.stringify` on the error object which would result in an empty object
- Removed ErrorParserUtility since it only works on specific error types. We can just log the full error message and manually derive information we need from the message.
- Added option to include stack trace in `getErrorMessage`. This is useful for figuring out where the client side script errors are coming from.
- Some minor refactors
