v0.1.22

Enhancements

• Rules Engine Customer resources may now be managed by using the associated Wholesaler or Partner credentials.

Bug Fixes

• Rules Engine service is now using the new API URL instead of the Legacy URL. No functional differences with the new API.

Full Changelog: v0.1.21...v0.1.22

v0.1.21

Enhancements

• CPS support is now available. See the examples examples/cps for implementation details.

Bug Fixes

• Fixed a bug where the SDK crashes if the EdgeCast API is inaccessible.

Full Changelog: v0.1.20...v0.1.21

v0.1.20

Breaking Changes

WAF Changes

Note: The README file and all WAF example files have been updated to reflect these changes.

• waf.WAFService has been renamed to waf.WafService.
• A new layer now exists between waf.WafService and the interfaces it exposes.
  For example, to add an access rule:

// Previous method
accessRuleID, err := wafService.AddAccessRule(waf.AddAccessRuleParams{
		AccountNumber: accountNumber,
		AccessRule:    waf.AccessRule{
			// ...
		},
	})

// Current method - notice ".AccessRules"
accessRuleID, err := wafService.AccessRules.AddAccessRule(
		access.AddAccessRuleParams{
			AccountNumber: accountNumber,
			AccessRule:    access.AccessRule{
				// ...
			}
		})

• In addition, there are WAF package changes. The waf package is no longer monolithic.
• waf/scopes contains all structs and functions pertaining to Security Application Management.
• waf/rules contains all common structs and functions for rules.
• Each rule type has its own package, e.g. Access Rules functionality exists in the waf/rules/access package.

Full Changelog: v0.1.19...v0.1.20

v0.1.19

What's Changed

Breaking Changes

RealTimeLogDeliveryAPI has been renamed to RtldService

Bug Fixes

Fixed a bug where Bot Manager Rule enum values were not serializing to strings.
The BotRuleDirective.SecRule property is now nullable - this fixed a bug in our Terraform Provider.

Full Changelog: v0.1.18...v0.1.19

v0.1.18

New Features

WAF Bot Manager is now available.

Breaking Changes

The waf.Directive struct used by waf.CustomRuleSet has been renamed to CustomRuleDirective. This serves to differentiate it from the new similar struct: waf.BotRuleDirective.

WAF Custom Rule Set properties that were once strings are now enum types. The underlying types are still strings.

1. waf.Action.Transformations: string => waf.Transformation
2. waf.Variable.Type: string => waf.VariableType
3. waf.Operator.Type: string => waf.OperatorType

Each new type comes with String() and case-insensitive ConvertTo___() functions to facilitate development.

s := "rx"

// ot == waf.OpRegexMatch
ot := waf.ConvertToOperatorType(s)

// s2 == "RX"
s2 := ot.String()

Enhancements

• A new Onboarding document has been added to help new contributors.
• The ReadMe has been updated to cover Bot Manager.

Full Changelog: v0.1.17...v0.1.18

v0.1.17

Bug Fixes and Enhancements

• Fixed an issue preventing updates to Customer Users
• Clarified in Customer example file that a Partner token needs to be used for Customer APIs

v0.1.16

Breaking Changes

1. Edgecast client and config were refactored necessitating changes to the instantiation process

• auth.OAuth2Credentials is now edgecast.IDSCredentials
• NewSDKConfig() no longer accepts parameters.
  Previous behavior: func NewSDKConfig(apiToken, OAuth2Credentials)
  New behavior: sdkConfig := edgecast.NewSDKConfig()
  sdkConfig.APIToken = "MY API TOKEN"
  sdkConfig.IDSCredentials = idsCredentials
• All WAFService methods now accept a single params object to match the behavior of the rest of the SDK services.
• Most NewAdd/Get/Update/Delete Params methods no longer return a pointer and corresponding functions to which these params are passed no longer accept a pointer. Remaining methods that return and pass pointers will be updated in a future release.
• logging package renamed to eclog

2. Internal changes not expected to be customer impacting

• BuildRequest() and SendRequest() deprecated in favor of a single SubmitRequest() method that takes a parameters struct with method, path, payload, and response object.
• auth and client packages renamed ecauth and ecclient
• collections package renamed to collectionhelper

New Features

• BETA Route DNS feature support (Master Server Group, Primary Zone, Secondary Zone Group, TSIG, Load Balancing and Failover Group)

Bug Fixes and Enhancements

• Refactor of Edgecast client to enhance testability and improve usability
• Example files updated to not require passing flags when running to improve usability
• Swagger generation templates updated to support Edgecast client refactor
• Architecture diagram added
• Readme file updated with supported features, project structure, and additional information covering recent enhancements
• Pull requests now test and build automatically
• New Linter enabled

v0.1.15

New Features

• Rules Engine support for Add Policy, Get Policy, and Submit Deploy Request
• Real-time Log Delivery (RTLD) support

Bug Fixes and Enhancements

• Enhanced logging in EdgeCast client
• ShowAsJson function to pretty print a JSON object
• Removed pointer reference in client response template

v0.1.14

New Features

• Support for Customer Origin management

Bug Fixes and Enhancements

• Created ecmodels package for models shared across features
• Refactored Edge CNAME to use shared Propagation ecmodel

v0.1.13

New Features

• Support for Edge CNAME management

Bug Fixes and Enhancements

• First iteration of enum-like implementation
• Removed QA environment URL from Customer example file